Add release CI workflow to build and release universal binary #55
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
codebytere
force-pushed
the
main
branch
3 times, most recently
from
e113096 to
4280ffc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a dedicated CI workflow for tagged releases.
Not only does it automate releases, it also enables publishing a universal binary which natively runs on both Intel and Apple Silicon machines, not need for Rosetta2.
It achieves this by first building two separate binaries for x64 and arm64 that are later combined into a single fat binary that supports both architectures.
Requirements:
In order to publish new releases, this CI workflow requires a repository secret called NPM_TOKEN which stores an npm automation access token.
How to use:
A new release will be published by pushing a new tag:
git tag -a v2.2.2 -m "Release v2.2.2" git push --tagsPlease note that this workflow will only run on tags that follow the form
v*.*.*, e.g.v2.2.2